AR V300R023SPH1b0
- Patch installation fails.
- The system time is inaccurate when the hardware clock fails.
- Interfaces on a 5G interface card cannot attach to networks after the card is upgraded.
- A device equipped with an LTE module and an interface card is disconnected after a version upgrade.
- Link flapping occurs after DH encryption is enabled and devices are restarted in an SD-WAN scenario.
- The peer device generates a MAC address flapping alarm.
- The hwExtAllMemberDownNotify alarm cannot be cleared after a device is restarted.
- If a third-party certificate is used, the identity certificate must be named default_local.cer.
- The command configuration fails to be delivered to a device and the device restarts unexpectedly.
- When multiple NMSs manage a device, there is a possibility that the device does not respond.
- A device restarts unexpectedly.
- In the scenario where both DHCP relay and IPsec are configured, when packets carry the non-fragmentation flag, the fragmentation flag and fragment offset are incorrect.
- Some NAT entries cannot be deleted.
- Tunnel flapping frequently occurs due to keepalive detection failures in an SD-WAN scenario.
- In an SD-WAN dual-gateway scenario, a large number of packets are lost when a single device is faulty.
- The NetStream function does not take effect.
- The VRRP preemption delay does not take effect.
- A dynamic BFD for DHCPv6 session flaps.
- When NAT flow logs are sent to a syslog server, the flow table time recorded in the logs is the UTC time, which cannot be changed to the local time.
- In an SD-WAN scenario, when an Ethernet physical interface is Up and its duplex mode is switched, no alarm or event is generated and sent to the controller.
- The dialer enable-circular and associated APN profile configurations are lost on a device using an LTE link for onboarding.
- A device reports the hwEthernetARPIPConflictEvent alarm after receiving a probe ARP packet whose destination IP address is the same as the IP address of an interface.
- In an SD-WAN scenario, the CPU usage of the control plane is high when performance data is reported.
- A device does not record the three source IP addresses with the largest number of sessions in the alarm that indicates the number of sessions exceeds the threshold.
- Internet access traffic fails to be forwarded when PBR is configured together with firewall services.
- Simplified deployment fails.
- After the interfaces connecting two devices are added to an E-Trunk, association between the interface status and BFD becomes abnormal.
- In an SD-WAN scenario, there is a possibility that link flapping occurs when a DH algorithm is used.
- Device registration with the controller times out or the controller fails to obtain device version information.
- When a device is powered off and restarted, the time recorded in the restart reason does not contain time zone information.
- A device restarts when the serial port redirection function is frequently used.
- When a device is powered off and restarted, the restart reason cannot be recorded.
- A device fails to obtain CRLs through HTTP.
- The compatibility of the algorithm for interconnection between devices and NCE-WAN V100R021 is defective, resulting in device onboarding failures.
- In an SD-WAN scenario with NAT traversal, the active and standby links are deployed on dual gateways, respectively. If the active link deployed on the active gateway is faulty and the standby link deployed on the standby gateway is deleted, the standby gateway does not re-enumerate links based on TNPs.